Clickx 115

home *** CD-ROM | disk | FTP | other *** search

/ Clickx 115 / Clickx 115.iso / software / tools / windows / tails-i386-0.16.iso / live / filesystem.squashfs / usr / share / doc / ferm / ferm.html < prev next >

Wrap

Extensible Markup Language | 2010-01-02 | 65.6 KB | 1,884 lines

<?xml version="1.0" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>B<ferm> - a firewall rule parser for linux</title> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <link rev="made" href="mailto:root@localhost" /> </head> <body style="background-color: white">  <div name="index"> <a name="__index__"></a> <ul> <li><a href="#name">NAME</a></li> <li><a href="#synopsis">SYNOPSIS</a></li> <li><a href="#description">DESCRIPTION</a></li> <li><a href="#caution">CAUTION</a></li> <li><a href="#introduction">INTRODUCTION</a></li> <li><a href="#structure_of_a_firewall_file">STRUCTURE OF A FIREWALL FILE</a></li> <ul> <li><a href="#keywords">Keywords</a></li> <li><a href="#parameters">Parameters</a></li> </ul> <li><a href="#basic_keywords">BASIC KEYWORDS</a></li> <ul> <li><a href="#location_keywords">Location keywords</a></li> <li><a href="#basic_iptables_match_keywords">Basic iptables match keywords</a></li> <li><a href="#basic_target_keywords">Basic target keywords</a></li> </ul> <li><a href="#additional_keywords">ADDITIONAL KEYWORDS</a></li> <ul> <li><a href="#iptables_match_modules">iptables match modules</a></li> <li><a href="#iptables_target_modules">iptables target modules</a></li> </ul> <li><a href="#other_domains">OTHER DOMAINS</a></li> <ul> <li><a href="#arptables_keywords">arptables keywords</a></li> <li><a href="#ebtables_keywords">ebtables keywords</a></li> </ul> <li><a href="#advanced_features">ADVANCED FEATURES</a></li> <ul> <li><a href="#variables">Variables</a></li> <li><a href="#automatic_variables">Automatic variables</a></li> <li><a href="#functions">Functions</a></li> <li><a href="#backticks">Backticks</a></li> <li><a href="#includes">Includes</a></li> <li><a href="#conditionals">Conditionals</a></li> <li><a href="#hooks">Hooks</a></li> </ul> <li><a href="#built_in_functions">BUILT-IN FUNCTIONS</a></li> <ul> <li><a href="#_resolve__hostname1_hostname2______">@resolve((hostname1 hostname2 ...))</a></li> </ul> <li><a href="#recipes">RECIPES</a></li> <ul> <li><a href="#easy_port_forwarding">Easy port forwarding</a></li> <li><a href="#remote_ferm">Remote ferm</a></li> </ul> <li><a href="#options">OPTIONS</a></li> <li><a href="#see_also">SEE ALSO</a></li> <li><a href="#requirements">REQUIREMENTS</a></li> <ul> <li><a href="#operating_system">Operating system</a></li> <li><a href="#software">Software</a></li> </ul> <li><a href="#bugs">BUGS</a></li> <li><a href="#copyright">COPYRIGHT</a></li> <li><a href="#author">AUTHOR</a></li> </ul> <hr name="index" /> </div>  <h1><a name="name">NAME</a></h1> ferm - a firewall rule parser for linux <hr /> <h1><a name="synopsis">SYNOPSIS</a></h1> ferm options inputfile <hr /> <h1><a name="description">DESCRIPTION</a></h1> ferm is a frontend for iptables. It reads the rules from a structured configuration file and calls <code>iptables(8)</code> to insert them into the running kernel. ferm's goal is to make firewall rules easy to write and easy to read. It tries to reduce the tedious task of writing down rules, thus enabling the firewall administrator to spend more time on developing good rules than the proper implementation of the rule. To achieve this, ferm uses a simple but powerful configuration language, which allows variables, functions, arrays, blocks. It also allows you to include other files, allowing you to create libraries of commonly used structures and functions. ferm, pronounced "firm", stands for "For Easy Rule Making". <hr /> <h1><a name="caution">CAUTION</a></h1> This manual page does not indend to teach you how firewalling works and how to write good rules. There is already enough documentation on this topic. <hr /> <h1><a name="introduction">INTRODUCTION</a></h1> Let's start with a simple example: <pre> chain INPUT { proto tcp ACCEPT; }</pre> This will add a rule to the predefined input chain, matching and accepting all tcp packets. Ok, let's make it more complicated: <pre> chain (INPUT OUTPUT) { proto (udp tcp) ACCEPT; }</pre> This will insert 4 rules, namely 2 in chain input, and 2 in chain output, matching and accepting both udp and tcp packets. Normally you would type this: <pre> iptables -A INPUT -p tcp -j ACCEPT iptables -A OUTPUT -p tcp -j ACCEPT iptables -A INPUT -p udp -j ACCEPT iptables -A OUTPUT -p udp -j ACCEPT</pre> Note how much less typing we need to do? :-) Basically, this is all there is to it, although you can make it quite more complex. Something to look at: <pre> chain INPUT { policy ACCEPT; daddr 10.0.0.0/8 proto tcp dport ! ftp jump mychain sport :1023 TOS 4 settos 8 mark 2; daddr 10.0.0.0/8 proto tcp dport ftp REJECT; }</pre> My point here is, that *you* need to make nice rules, keep them readable to you and others, and not make it into a mess. It would aid the reader if the resulting firewall rules were placed here for reference. Also, you could include the nested version with better readability. Try using comments to show what you are doing: <pre> # this line enables transparent http-proxying for the internal network: proto tcp if eth0 daddr ! 192.168.0.0/255.255.255.0 dport http REDIRECT to-ports 3128;</pre> You will be thankful for it later! <pre> chain INPUT { policy ACCEPT; interface (eth0 ppp0) { # deny access to notorius hackers, return here if no match # was found to resume normal firewalling jump badguys;</pre> <pre> protocol tcp jump fw_tcp; protocol udp jump fw_udp; } }</pre> The more you nest, the better it looks. Make sure the order you specify is correct, you would not want to do this: <pre> chain FORWARD { proto ! udp DROP; proto tcp dport ftp ACCEPT; }</pre> because the second rule will never match. Best way is to specify first everyting that is allowed, and then deny everything else. Look at the examples for more good snapshots. Most people do something like this: <pre> proto tcp { dport ( ssh http ftp ) ACCEPT; dport 1024:65535 ! syn ACCEPT; DROP; }</pre> <hr /> <h1><a name="structure_of_a_firewall_file">STRUCTURE OF A FIREWALL FILE</a></h1> The structure of a proper firewall file looks like simplified C-code. Only a few syntactic characters are used in ferm- configuration files. Besides these special caracters, ferm uses 'keys' and 'values', think of them as options and parameters, or as variables and values, whatever. With these words, you define the characteristics of your firewall. Every firewall consists of two things: First, look if network traffic matches certain conditions, and second, what to do with that traffic. You may specify conditions that are valid for the kernel interface program you are using, probably <code>iptables(8)</code>. For instance, in iptables, when you are trying to match tcp packets, you would say: <pre> iptables --protocol tcp</pre> In ferm, this will become: <pre> protocol tcp;</pre> Just typing this in ferm doesn't do anything, you need to tell ferm (actually, you need to tell <code>iptables(8)</code> and the kernel) what to do with any traffic that matches this condition: <pre> iptables --protocol tcp -j ACCEPT</pre> Or, translated to ferm: <pre> protocol tcp ACCEPT;</pre> The ; character is at the end of every ferm rule. Ferm ignores line breaks, meaning the above example is identical to the following: <pre> protocol tcp ACCEPT;</pre> Here's a list of the special characters: <dl> <dt><a name="_" class="item">;</a></dt> <dd> This character finalizes a rule. Separated by semicolons, you may write multiple rules in one line, although this decreases readability: <pre> protocol tcp ACCEPT; protocol udp DROP;</pre> </dd> <dt><a name="__" class="item">{}</a></dt> <dd> The nesting symbol defines a 'block' of rules. The curly brackets contain any number of nested rules. All matches before the block are carried forward to these. The closing curly bracket finalizes the rule set. You should not write a ';' after that, because that would be an empty rule. Example: <pre> chain INPUT proto icmp { icmp-type echo-request ACCEPT; DROP; }</pre> This block shows two rules inside a block, which will both be merged with anything in front of it, so you will get two rules: <pre> iptables -A INPUT -p icmp --icmp-type echo-request -j ACCEPT iptables -A INPUT -p icmp -j DROP</pre> There can be multiple nesting levels: <pre> chain INPUT { proto icmp { icmp-type echo-request ACCEPT; DROP; } daddr 172.16.0.0/12 REJECT; }</pre> Note that the 'REJECT' rule is not affected by 'proto icmp', although there is no ';' after the closing curly brace. Translated to iptables: <pre> iptables -A INPUT -p icmp --icmp-type echo-request -j ACCEPT iptables -A INPUT -p icmp -j DROP iptables -A INPUT -d 172.16.0.0/12 -j REJECT</pre> </dd> <dt><a name="_" class="item">$</a></dt> <dd> Variable expansion. Replaces '$FOO' by the value of the variable. See the section VARIABLES for details. </dd> <dt><a name="_" class="item">&</a></dt> <dd> Function call. See the section FUNCTIONS for details. </dd> <dt><a name="__" class="item">()</a></dt> <dd> The array symbol. Using the parentheses, you can define a 'list' of values that should be applied for the key to the left of it. Example: <pre> protocol ( tcp udp icmp )</pre> this will result in three rules: <pre> ... -p tcp ... ... -p udp ... ... -p icmp ...</pre> Only values can be 'listed', so you cannot do something like this: <pre> proto tcp ( ACCEPT LOG );</pre> but you can do this: <pre> chain (INPUT OUTPUT FORWARD) proto (icmp udp tcp) DROP;</pre> (which will result in nine rules!) Values are separated by spaces. The array symbol is both left- and right-associative, in contrast with the nesting block, which is left-associative only. </dd> <dt><a name="_" class="item"><code> # </code></a></dt> <dd> The comment symbol. Anything that follows this symbol up to the end of line is ignored. </dd> <dt><a name="command" class="item"><code>`command`</code></a></dt> <dd> Execute the command in a shell, and insert the process output. See the section backticks for details. </dd> <dt><a name="string" class="item"><code>'string'</code></a></dt> <dd> Quote a string which may contain whitespaces, the dollar sign etc. <pre> LOG log-prefix ' hey, this is my log prefix!';</pre> </dd> <dt><a name="string2" class="item"><a href="#string"><code>"string"</code></a></a></dt> <dd> Quote a string (see above), but variable references with a dollar sign are evaluated: <pre> DNAT to "$myhost:$myport";</pre> </dd> </dl> <h2><a name="keywords">Keywords</a></h2> In the previous section, we already introduced some basic keywords like "chain", "protocol" and "ACCEPT". Let's explore their nature. There are three kinds of keywords: <dl> <dt> <dd> location keywords define where a rule will be created. Example: "table", "chain". </dd> <dt> <dd> match keywords perform a test on all passing packets. The current rule is without effect if one (or more) of the matches does not pass. Example: "proto", "daddr". Most matches are followed by a parameter: "proto tcp", "daddr 172.16.0.0/12". </dd> <dt> <dd> target keywords state what to do with a packet. Example: "ACCEPT", "REJECT", "jump". Some targets define more keywords to specify details: "REJECT reject-with icmp-net-unreachable". </dd> </dl> Every rule consists of a location and a target, plus any number of matches: <pre> table filter # location proto tcp dport (http https) # match ACCEPT; # target</pre> Strictly speaking, there is a fourth kind: ferm keywords (which control ferm's internal behaviour), but they will be explained later. <h2><a name="parameters">Parameters</a></h2> Many keywords take parameters. These can be specified as literals, variable references or lists (arrays): <pre> proto udp saddr %TRUSTED_HOSTS; proto tcp dport (http https ssh); LOG log-prefix "funky wardriver alert: ";</pre> Some of them can be negated (lists cannot be negated): <pre> proto !esp; proto udp dport !domain;</pre> Keywords which take no parameters are negated by a prefixed '!': <pre> proto tcp !syn;</pre> Read <code>iptables(8)</code> to see where the ! can be used. <hr /> <h1><a name="basic_keywords">BASIC KEYWORDS</a></h1> <h2><a name="location_keywords">Location keywords</a></h2> <dl> <dt><a name="domain_ip_ip6" class="item">domain [ip|ip6]</a></dt> <dd> Set the domain. "ip" is default and means "IPv4" (iptables). "ip6" is for IPv6 support, using "ip6tables". </dd> <dt><a name="table_filter_nat_mangle" class="item">table [filter|nat|mangle]</a></dt> <dd> Specifies which netfilter table this rule will be inserted to: "filter" (default), "nat" or "mangle". </dd> <dt><a name="chain_chain_name" class="item">chain [chain-name]</a></dt> <dd> Specifies the netfilter chain (within the current table) this rule will be inserted to. Common predefined chain names are "INPUT", "OUTPUT", "FORWARD", "PREROUTING", "POSTROUTING", depending on the table. See the netfilter documentation for details. If you specify a non-existing chain here, ferm will add the rule to a custom chain with that name. </dd> <dt><a name="policy_accept_drop" class="item">policy [ACCEPT|DROP|..]</a></dt> <dd> Specifies the default policy for the current chain (built-in only). Can be one of the built-in targets (ACCEPT, DROP, REJECT, ...). A packet that matches no rules in a chain will be treated as specified by the policy. To avoid ambiguity, always specify the policies of all predefined chains explicitly. </dd> <dt><a name="_subchain" class="item">@subchain ["CHAIN-NAME"] { ... }</a></dt> <dd> Works like the normal block operators (i.e. without the @subchain keyword), except that ferm moves rules within the curly braces into a new custom chain. The name for this chain is chosen automatically by ferm. In many cases, this is faster than just a block, because the kernel may skip a huge block of rules when a precondition is false. Imagine the following example: <pre> table filter chain INPUT { saddr (1.2.3.4 2.3.4.5 3.4.5.6 4.5.6.7 5.6.7.8) { proto tcp dport (http https ssh) ACCEPT; proto udp dport domain ACCEPT; } }</pre> This generates 20 rules. When a packet arrives which does not pass the saddr match, it nonetheless checks all 20 rules. With @subchain, this check is done once, resulting in faster network filtering and less CPU load: <pre> table filter chain INPUT { saddr (1.2.3.4 2.3.4.5 3.4.5.6 4.5.6.7 5.6.7.8) @subchain { proto tcp dport (http https ssh) ACCEPT; proto udp dport domain ACCEPT; } }</pre> Optionally, you may define the name of the sub chain: <pre> saddr (1.2.3.4 2.3.4.5 3.4.5.6) @subchain "foobar" { proto tcp dport (http https ssh) ACCEPT; proto udp dport domain ACCEPT; }</pre> You can achieve the same by explicitly declaring a custom chain, but you may feel that using @subchain requires less typing. </dd> </dl> <h2><a name="basic_iptables_match_keywords">Basic iptables match keywords</a></h2> <dl> <dt><a name="interface_interface_name" class="item">interface [interface-name]</a></dt> <dd> Define the interface name, your outside network card, like eth0, or dialup like ppp1, or whatever device you want to match for passing packets. It is equivalent to the <code>-i</code> switch in <code>iptables(8)</code>. </dd> <dt><a name="outerface_interface_name" class="item">outerface [interface-name]</a></dt> <dd> Same as interface, only for matching the outgoing interface for a packet, as in <code>iptables(8)</code>. </dd> <dt><a name="protocol_protocol_name_protocol_number" class="item">protocol [protocol-name|protocol-number]</a></dt> <dd> Currently supported by the kernel are tcp, udp and icmp, or their respective numbers. </dd> <dt><a name="saddr_daddr_address_spec" class="item">saddr|daddr [address-spec]</a></dt> <dd> Matches on packets originating from the specified address (saddr) or targeted at the address (daddr). Examples: <pre> saddr 192.168/8 ACCEPT; # (identical to the next one:) saddr 192.168.0.0/255.255.255.0 ACCEPT; daddr my.domain.com ACCEPT;</pre> </dd> <dt><a name="fragment" class="item">fragment</a></dt> <dd> Specify that only fragmented IP packets should be matched. When packets are larger that the maximum packet size your system can handle (called Maximum Transmission Unit or MTU) they will be chopped into bits and sent one by one as single packets. See <code>ifconfig(8)</code> if you want to find the MTU for your system (the default is usually 1500 bytes). Fragments are frequently used in DOS attacks, because there is no way of finding out the origin of a fragment packet. </dd> <dt><a name="sport_dport_port_spec" class="item">sport|dport [port-spec]</a></dt> <dd> Matches on packets on the specified TCP or UDP port. "sport" matches the source port, and dport matches the destination port. This match can be used only after you specified "protocol tcp" or "protocol udp", because only these two protocols actually have ports. And some examples of valid ports/ranges: <pre> dport 80 ACCEPT; dport http ACCEPT; dport ssh:http ACCEPT; dport 0:1023 ACCEPT; # equivalent to :1023 dport 1023:65535 ACCEPT;</pre> </dd> <dt><a name="syn" class="item">syn</a></dt> <dd> Specify that the SYN flag in a tcp package should be matched, which are used to build new tcp connections. You can identify incoming connections with this, and decide wether you want to allow it or not. Packets that do not have this flag are probably from an already established connection, so it's considered reasonably safe to let these through. </dd> <dt><a name="module_module_name" class="item">module [module-name]</a></dt> <dd> Load an iptables module. Most modules provide more match keywords. We'll get to that later. </dd> </dl> <h2><a name="basic_target_keywords">Basic target keywords</a></h2> <dl> <dt><a name="jump_custom_chain_name" class="item">jump [custom-chain-name]</a></dt> <dd> Jumps to a custom chain. If no rule in the custom chain matched, netfilter returns to the next rule in the previous chain. </dd> <dt><a name="realgoto_custom_chain_name" class="item">realgoto [custom-chain-name]</a></dt> <dd> Go to a custom chain. Unlike the jump option, RETURN will not continue processing in this chain but instead in the chain that called us via jump. The keyword realgoto was chosen during the transition period, because goto (already deprecated) used to be an alias for jump. </dd> <dt><a name="accept" class="item">ACCEPT</a></dt> <dd> Accepts matching packets. </dd> <dt><a name="drop" class="item">DROP</a></dt> <dd> Drop matching packets without further notice. </dd> <dt><a name="reject" class="item">REJECT</a></dt> <dd> Rejects matching packets, i.e. send an ICMP packet to the sender, which is port-unreachable by default. You may specify another ICMP type. <pre> REJECT; # default to icmp-port-unreachable REJECT reject-with icmp-net-unreachable;</pre> Type "iptables -j REJECT -h" for details. </dd> <dt><a name="return" class="item">RETURN</a></dt> <dd> Finish the current chain and return to the calling chain (if "jump [custom-chain-name]" was used). </dd> <dt><a name="nop" class="item">NOP</a></dt> <dd> No action at all. </dd> </dl> <hr /> <h1><a name="additional_keywords">ADDITIONAL KEYWORDS</a></h1> Netfilter is modular. Modules may provide additional targets and match keywords. The list of netfilter modules is constantly growing, and ferm tries to keep up with supporting them all. This chapter describes modules which are currently supported. <h2><a name="iptables_match_modules">iptables match modules</a></h2> <dl> <dt><a name="account" class="item">account</a></dt> <dd> Account traffic for all hosts in defined network/netmask. This is one of the match modules which behave like a target, i.e. you will mostly have to use the NOP target. <pre> mod account aname mynetwork aaddr 192.168.1.0/24 ashort NOP;</pre> </dd> <dt><a name="addrtype" class="item">addrtype</a></dt> <dd> Check the address type; either source address or destination address. <pre> mod addrtype src-type BROADCAST; mod addrtype dst-type LOCAL;</pre> Type "iptables -m addrtype -h" for details. </dd> <dt><a name="ah" class="item">ah</a></dt> <dd> Checks the SPI header in an AH packet. <pre> mod ah ahspi 0x101; mod ah ahspi ! 0x200:0x2ff;</pre> Additional arguments for IPv6: <pre> mod ah ahlen 32 ACCEPT; mod ah ahlen !32 ACCEPT; mod ah ahres ACCEPT;</pre> </dd> <dt><a name="comment" class="item">comment</a></dt> <dd> Adds a comment of up to 256 characters to a rule, without an effect. Note that unlike ferm comments ('#'), this one will show up in "iptables -L". <pre> mod comment comment "This is my comment." ACCEPT;</pre> </dd> <dt><a name="condition" class="item">condition</a></dt> <dd> Matches if a value in /proc/net/ipt_condition/NAME is 1 (path is /proc/net/ip6t_condition/NAME for the ip6 domain). <pre> mod condition condition (abc def) ACCEPT; mod condition condition !foo ACCEPT;</pre> </dd> <dt><a name="connbytes" class="item">connbytes</a></dt> <dd> Match by how many bytes or packets a connection (or one of the two flows constituting the connection) have tranferred so far, or by average bytes per packet. <pre> mod connbytes connbytes 65536: connbytes-dir both connbytes-mode bytes ACCEPT; mod connbytes connbytes !1024:2048 connbytes-dir reply connbytes-mode packets ACCEPT;</pre> Valid values for connbytes-dir: original, reply, both; for connbytes-mode: packets, bytes, avgpkt. </dd> <dt><a name="connlimit" class="item">connlimit</a></dt> <dd> Allows you to restrict the number of parallel TCP connections to a server per client IP address (or address block). <pre> mod connlimit connlimit-above 4 REJECT; mod connlimit connlimit-above !4 ACCEPT; mod connlimit connlimit-above 4 connlimit-mask 24 REJECT;</pre> </dd> <dt><a name="connmark" class="item">connmark</a></dt> <dd> Check the mark field associated with the connection, set by the CONNMARK target. <pre> mod connmark mark 64; mod connmark mark 6/7;</pre> </dd> <dt><a name="conntrack" class="item">conntrack</a></dt> <dd> Check connection tracking information. <pre> mod conntrack ctstate (ESTABLISHED RELATED); mod conntrack ctproto tcp; mod conntrack ctorigsrc 192.168.0.2; mod conntrack ctorigdst 1.2.3.0/24; mod conntrack ctreplsrc 2.3.4.5; mod conntrack ctrepldst ! 3.4.5.6; mod conntrack ctstatus ASSURED; mod conntrack ctexpire 60; mod conntrack ctexpire 180:240;</pre> Type "iptables -m conntrack -h" for details. </dd> <dt><a name="dccp" class="item">dccp</a></dt> <dd> Check DCCP (Datagram Congestion Control Protocol) specific attributes. This module is automatically loaded when you use "protocol dccp". <pre> proto dccp sport 1234 dport 2345 ACCEPT; proto dccp dccp-types (SYNCACK ACK) ACCEPT; proto dccp dccp-types !REQUEST DROP; proto dccp dccp-option 2 ACCEPT;</pre> </dd> <dt><a name="dscp" class="item">dscp</a></dt> <dd> Match the 6 bit DSCP field within the TOS field. <pre> mod dscp dscp 11; mod dscp dscp-class AF41;</pre> </dd> <dt><a name="dst" class="item">dst</a></dt> <dd> Matches the Destination Options header (ip6). <pre> mod dst dst-len 8 ACCEPT; mod dst dst-len !8 ACCEPT; mod dst dst-opts (1:4 2:8) ACCEPT;</pre> </dd> <dt><a name="ecn" class="item">ecn</a></dt> <dd> Match the ECN bits of an IPv4 TCP header. <pre> mod ecn ecn-tcp-cwr; mod ecn ecn-tcp-ece; mod ecn ecn-ip-ect 2;</pre> Type "iptables -m ecn -h" for details. </dd> <dt><a name="esp" class="item">esp</a></dt> <dd> Checks the SPI header in an ESP packet. <pre> mod esp espspi 0x101; mod esp espspi ! 0x200:0x2ff;</pre> </dd> <dt><a name="eui64" class="item">eui64</a></dt> <dd> "This module matches the EUI-64 part of a stateless autoconfigured IPv6 address. It compares the EUI-64 derived from the source MAC address in Ehternet frame with the lower 64 bits of the IPv6 source address. But "Universal/Local" bit is not compared. This module doesn't match other link layer frame, and is only valid in the PREROUTING, INPUT and FORWARD chains." <pre> mod eui64 ACCEPT;</pre> </dd> <dt><a name="frag" class="item">frag</a></dt> <dd> Matches the Fragment header (ip6). <pre> mod frag fragid 123:456 ACCEPT; mod frag fragid !123:456 ACCEPT; mod frag fragres ACCEPT; mod frag fragfirst ACCEPT; mod frag fragmore ACCEPT; mod frag fraglast ACCEPT;</pre> </dd> <dt><a name="fuzzy" class="item">fuzzy</a></dt> <dd> "This module matches a rate limit based on a fuzzy logic controller [FLC]." <pre> mod fuzzy lower-limit 10 upper-limit 20 ACCEPT;</pre> </dd> <dt><a name="hbh" class="item">hbh</a></dt> <dd> Matches the Hop-by-Hop Options header (ip6). <pre> mod hbh hbh-len 8 ACCEPT; mod hbh hbh-len !8 ACCEPT; mod hbh hbh-opts (1:4 2:8) ACCEPT;</pre> </dd> <dt><a name="hl" class="item">hl</a></dt> <dd> Matches the Hop Limit field (ip6). <pre> mod hl hl-eq (8 10) ACCEPT; mod hl hl-eq !5 ACCEPT; mod hl hl-gt 15 ACCEPT; mod hl hl-lt 2 ACCEPT;</pre> </dd> <dt><a name="helper" class="item">helper</a></dt> <dd> Checks which conntrack helper module tracks this connection. The port may be specified with "-portnr". <pre> mod helper helper irc ACCEPT; mod helper helper ftp-21 ACCEPT;</pre> </dd> <dt><a name="icmp" class="item">icmp</a></dt> <dd> Check ICMP specific attributes. This module is automatically loaded when you use "protocol icmp". <pre> proto icmp icmp-type echo-request ACCEPT;</pre> This option can also be used in be ip6 domain, although this is called icmpv6 in ip6tables. Use "iptables -p icmp <code>-h</code>" to obtain a list of valid ICMP types. </dd> <dt><a name="iprange" class="item">iprange</a></dt> <dd> Match a range of IPv4 addresses. <pre> mod iprange src-range 192.168.2.0-192.168.3.255; mod iprange dst-range ! 192.168.6.0-192.168.6.255;</pre> </dd> <dt><a name="ipv4options" class="item">ipv4options</a></dt> <dd> Match on IPv4 header options like source routing, record route, timestamp and router-alert. <pre> mod ipv4options ssrr ACCEPT; mod ipv4options lsrr ACCEPT; mod ipv4options no-srr ACCEPT; mod ipv4options !rr ACCEPT; mod ipv4options !ts ACCEPT; mod ipv4options !ra ACCEPT; mod ipv4options !any-opt ACCEPT;</pre> </dd> <dt><a name="ipv6header" class="item">ipv6header</a></dt> <dd> Matches the IPv6 extension header (ip6). <pre> mod ipv6header header !(hop frag) ACCEPT; mod ipv6header header (auth dst) ACCEPT;</pre> </dd> <dt><a name="hashlimit" class="item">hashlimit</a></dt> <dd> Similar to 'mod limit', but adds the ability to add per-destination or per-port limits managed in a hash table. <pre> mod hashlimit hashlimit 10/minute hashlimit-burst 30/minute hashlimit-mode dstip hashlimit-name foobar ACCEPT;</pre> Possible values for hashlimit-mode: dstip dstport srcip srcport. There are more possible settings, type "iptables -m hashlimit -h" for documentation. </dd> <dt><a name="length" class="item">length</a></dt> <dd> Check the package length. <pre> mod length length 128; # exactly 128 bytes mod length length 512:768; # range mod length length ! 256; # negated</pre> </dd> <dt><a name="limit" class="item">limit</a></dt> <dd> Limits the packet rate. <pre> mod limit limit 1/second; mod limit limit 15/minute limit-burst 10;</pre> Type "iptables -m limit -h" for details. </dd> <dt><a name="mac" class="item">mac</a></dt> <dd> Match the source MAC address. <pre> mod mac mac-source 01:23:45:67:89;</pre> </dd> <dt><a name="mark" class="item">mark</a></dt> <dd> Matches packets based on their netfilter mark field. This may be a 32 bit integer between 0 and 4294967295. <pre> mod mark mark 42;</pre> </dd> <dt><a name="mh" class="item">mh</a></dt> <dd> Matches the mobility header (domain ip6). <pre> proto mh mh-type binding-update ACCEPT;</pre> </dd> <dt><a name="multiport" class="item">multiport</a></dt> <dd> Match a set of source or destination ports (UDP and TCP only). <pre> mod multiport source-ports (https ftp); mod multiport destination-ports (mysql domain);</pre> This rule has a big advantage over "dport" and "sport": it generates only one rule for up to 15 ports instead of one rule for every port. </dd> <dt><a name="nth" class="item">nth</a></dt> <dd> Match every 'n'th packet. <pre> mod nth every 3; mod nth counter 5 every 2; mod nth start 2 every 3; mod nth start 5 packet 2 every 6;</pre> Type "iptables -m nth -h" for details. </dd> <dt><a name="owner" class="item">owner</a></dt> <dd> Check information about the packet creator, namely user id, group id, process id, session id and command name. <pre> mod owner uid-owner 0; mod owner gid-owner 1000; mod owner pid-owner 5432; mod owner sid-owner 6543; mod owner cmd-owner "sendmail";</pre> ("cmd-owner", "pid-owner" and "sid-owner" require special kernel patches not included in the vanilla Linux kernel) </dd> <dt><a name="physdev" class="item">physdev</a></dt> <dd> Matches the physical device on which a packet entered or is about to leave the machine. This is useful for bridged interfaces. <pre> mod physdev physdev-in ppp1; mod physdev physdev-out eth2; mod physdev physdev-is-in; mod physdev physdev-is-out; mod physdev physdev-is-bridged;</pre> </dd> <dt><a name="pkttype" class="item">pkttype</a></dt> <dd> Check the link-layer packet type. <pre> mod pkttype pkt-type unicast; mod pkttype pkt-type broadcase; mod pkttype pkt-type multicast;</pre> </dd> <dt><a name="policy" class="item">policy</a></dt> <dd> Matches IPsec policy being applied to this packet. <pre> mod policy dir out pol ipsec ACCEPT; mod policy strict reqid 23 spi 0x10 proto ah ACCEPT; mod policy mode tunnel tunnel-src 192.168.1.2 ACCEPT; mod policy mode tunnel tunnel-dst 192.168.2.1 ACCEPT; mod policy strict next reqid 24 spi 0x11 ACCEPT;</pre> Note that the keyword proto is also used as a shorthand version of protocol (built-in match module). You can fix this conflict by always using the long keyword protocol. </dd> <dt><a name="psd" class="item">psd</a></dt> <dd> Detect TCP/UDP port scans. <pre> mod psd psd-weight-threshold 21 psd-delay-threshold 300 psd-lo-ports-weight 3 psd-hi-ports-weight 1 DROP;</pre> </dd> <dt><a name="quota" class="item">quota</a></dt> <dd> Implements network quotas by decrementing a byte counter with each packet. <pre> mod quota quota 65536 ACCEPT;</pre> </dd> <dt><a name="random" class="item">random</a></dt> <dd> Match a random percentage of all packets. <pre> mod random average 70;</pre> </dd> <dt><a name="realm" class="item">realm</a></dt> <dd> Match the routing realm. Useful in environments using BGP. <pre> mod realm realm 3;</pre> </dd> <dt><a name="recent" class="item">recent</a></dt> <dd> Temporarily mark source IP addresses. <pre> mod recent set; mod recent rcheck seconds 60; mod recent set rsource name "badguy"; mod recent set rdest; mod recent rcheck rsource name "badguy" seconds 60; mod recent update seconds 120 hitcount 3 rttl;</pre> This netfilter module has a design flaw: although it is implemented as a match module, it has target-like behaviour when using the "set" keyword. <a href="http://snowman.net/projects/ipt_recent/">http://snowman.net/projects/ipt_recent/</a> </dd> <dt><a name="rt" class="item">rt</a></dt> <dd> Match the IPv6 routing header (ip6 only). <pre> mod rt rt-type 2 rt-len 20 ACCEPT; mod rt rt-type !2 rt-len !20 ACCEPT; mod rt rt-segsleft 2:3 ACCEPT; mod rt rt-segsleft !4:5 ACCEPT; mod rt rt-0-res rt-0-addrs (::1 ::2) rt-0-not-strict ACCEPT;</pre> </dd> <dt><a name="sctp" class="item">sctp</a></dt> <dd> Check SCTP (Stream Control Transmission Protocol) specific attributes. This module is automatically loaded when you use "protocol sctp". <pre> proto sctp sport 1234 dport 2345 ACCEPT; proto sctp chunk-types only DATA:Be ACCEPT; proto sctp chunk-types any (INIT INIT_ACK) ACCEPT; proto sctp chunk-types !all (HEARTBEAT) ACCEPT;</pre> Use "iptables -p sctp <code>-h</code>" to obtain a list of valid chunk types. </dd> <dt><a name="set" class="item">set</a></dt> <dd> Checks the source or destination IP/Port/MAC against a set. <pre> mod set set badguys src DROP;</pre> See <a href="http://ipset.netfilter.org/">http://ipset.netfilter.org/</a> for more information. </dd> <dt><a name="state" class="item">state</a></dt> <dd> Checks the connection tracking state. <pre> mod state state INVALID DROP; mod state state (ESTABLISHED RELATED) ACCEPT;</pre> Type "iptables -m state -h" for details. </dd> <dt><a name="statistic" class="item">statistic</a></dt> <dd> Successor of nth and random, currently undocumented in the <code>iptables(8)</code> man page. <pre> mod statistic mode random probability 0.8 ACCEPT; mod statistic mode nth every 5 packet 0 DROP;</pre> </dd> <dt>string</dt> <dd> Matches a string. <pre> mod string string "foo bar" ACCEPT; mod string algo kmp from 64 to 128 hex-string "deadbeef" ACCEPT;</pre> </dd> <dt><a name="tcp" class="item">tcp</a></dt> <dd> Checks TCP specific attributes. This module is automatically loaded when you use "protocol tcp". <pre> proto tcp sport 1234; proto tcp dport 2345; proto tcp tcp-flags (SYN ACK) SYN; proto tcp tcp-flags ! (SYN ACK) SYN; proto tcp tcp-flags ALL (RST ACK); proto tcp syn; proto tcp tcp-option 2; proto tcp mss 512;</pre> Type "iptables -p tcp -h" for details. </dd> <dt><a name="tcpmss" class="item">tcpmss</a></dt> <dd> Check the TCP MSS field of a SYN or SYN/ACK packet. <pre> mod tcpmss mss 123 ACCEPT; mod tcpmss mss 234:567 ACCEPT;</pre> </dd> <dt><a name="time" class="item">time</a></dt> <dd> Check if the time a packet arrives is in given range. <pre> mod time timestart 12:00; mod time timestop 13:30; mod time days (Mon Wed Fri); mod time datestart 2005:01:01; mod time datestart 2005:01:01:23:59:59; mod time datestop 2005:04:01; mod time monthday (30 31); mod time weekdays (Wed Thu); mod time timestart 12:00 utc; mod time timestart 12:00 localtz;</pre> Type "iptables -m time -h" for details. </dd> <dt><a name="tos" class="item">tos</a></dt> <dd> Matches a packet on the specified TOS-value. <pre> mod tos tos Minimize-Cost ACCEPT; mod tos tos !Normal-Service ACCEPT;</pre> Type "iptables -m tos -h" for details. </dd> <dt><a name="ttl" class="item">ttl</a></dt> <dd> Matches the ttl (time to live) field in the IP header. <pre> mod ttl ttl-eq 12; # ttl equals mod ttl ttl-gt 10; # ttl greater than mod ttl ttl-lt 16; # ttl less than</pre> </dd> <dt><a name="u32" class="item">u32</a></dt> <dd> Compares raw data from the packet. You can specify more than one filter in a ferm list; these are not expanded into multiple rules. <pre> mod u32 u32 '6&0xFF=1' ACCEPT; mod u32 u32 ('27&0x8f=7' '31=0x527c4833') DROP;</pre> </dd> <dt><a name="unclean" class="item">unclean</a></dt> <dd> Matches packets which seem malformed or unusual. This match has no further parameters. </dd> </dl> <h2><a name="iptables_target_modules">iptables target modules</a></h2> The following additional targets are available in ferm, provided that you enabled them in your kernel: <dl> <dt><a name="classify" class="item">CLASSIFY</a></dt> <dd> Set the CBQ class. <pre> CLASSIFY set-class 3:50;</pre> </dd> <dt><a name="clusterip" class="item">CLUSTERIP</a></dt> <dd> Configure a simple cluster of nodes that share a certain IP and MAC address. Connections are statically distributed between the nodes. <pre> CLUSTERIP new hashmode sourceip clustermac 00:12:34:45:67:89 total-nodes 4 local-node 2 hash-init 12345;</pre> </dd> <dt><a name="connmark" class="item">CONNMARK</a></dt> <dd> Sets the netfilter mark value associated with a connection. <pre> CONNMARK set-mark 42; CONNMARK save-mark; CONNMARK restore-mark; CONNMARK save-mark mask 0x7fff; CONNMARK restore-mark mask 0x8000;</pre> </dd> <dt><a name="connsecmark" class="item">CONNSECMARK</a></dt> <dd> This module copies security markings from packets to connections (if unlabeled), and from connections back to packets (also only if unlabeled). Typically used in conjunction with SECMARK, it is only valid in the mangle table. <pre> CONNSECMARK save; CONNSECMARK restore;</pre> </dd> <dt><a name="dnat_to_ip_address_ip_range_ip_port_range" class="item">DNAT to [ip-address|ip-range|ip-port-range]</a></dt> <dd> Change the destination address of the packet. <pre> DNAT to 10.0.0.4; DNAT to 10.0.0.4:80; DNAT to 10.0.0.4:1024-2048; DNAT to 10.0.1.1-10.0.1.20;</pre> </dd> <dt><a name="ecn" class="item">ECN</a></dt> <dd> This target allows to selectively work around known ECN blackholes. It can only be used in the mangle table. <pre> ECN ecn-tcp-remove;</pre> </dd> <dt><a name="hl" class="item">HL</a></dt> <dd> Modify the IPv6 Hop Limit field (ip6/mangle only). <pre> HL hl-set 5; HL hl-dec 2; HL hl-inc 1;</pre> </dd> <dt><a name="ipv4optsstrip" class="item">IPV4OPTSSTRIP</a></dt> <dd> Strip all the IP options from a packet. This module does not take any options. <pre> IPV4OPTSSTRIP;</pre> </dd> <dt><a name="log" class="item">LOG</a></dt> <dd> Log all packets that match this rule in the kernel log. Be carefull with log flooding. Note that this is a "non-terminating target", i.e. rule traversal continues at the next rule. <pre> LOG log-level warning log-prefix "Look at this: "; LOG log-tcp-sequence log-tcp-options; LOG log-ip-options;</pre> </dd> <dt><a name="mark" class="item">MARK</a></dt> <dd> Sets the netfilter mark field for the packet (a 32 bit integer between 0 and 4294967295): <pre> MARK set-mark 42; MARK set-xmark 7/3; MARK and-mark 31; MARK or-mark 1; MARK xor-mark 12;</pre> </dd> <dt><a name="masquerade" class="item">MASQUERADE</a></dt> <dd> Masquerades matching packets. Optionally followed by a port or port-range for iptables. Specify as "123", "123-456" or "123:456". The port range parameter specifies what local ports masqueraded connections should originate from. <pre> MASQUERADE; MASQUERADE to-ports 1234:2345; MASQUERADE to-ports 1234:2345 random;</pre> </dd> <dt><a name="mirror" class="item">MIRROR</a></dt> <dd> Experimental demonstration target which inverts the source and destination fields in the IP header. <pre> MIRROR;</pre> </dd> <dt><a name="netmap" class="item">NETMAP</a></dt> <dd> Map a whole network onto another network in the nat table. <pre> NETMAP to 192.168.2.0/24;</pre> </dd> <dt><a name="notrack" class="item">NOTRACK</a></dt> <dd> Disable connection tracking for all packets matching that rule. <pre> proto tcp dport (135:139 445) NOTRACK;</pre> </dd> <dt><a name="nflog" class="item">NFLOG</a></dt> <dd> Log packets over netlink; this is the successor of ULOG. <pre> NFLOG nflog-group 5 nflog-prefix "Look at this: "; NFLOG nflog-range 256; NFLOG nflog-threshold 10;</pre> </dd> <dt><a name="nfqueue" class="item">NFQUEUE</a></dt> <dd> Userspace queueing, requires nfnetlink_queue kernel support. <pre> proto tcp dport ftp NFQUEUE queue-num 20;</pre> </dd> <dt><a name="queue" class="item">QUEUE</a></dt> <dd> Userspace queueing, the predecessor to NFQUEUE. All packets go to queue 0. <pre> proto tcp dport ftp QUEUE;</pre> </dd> <dt><a name="redirect_to_ports_ports" class="item">REDIRECT to-ports [ports]</a></dt> <dd> Transparent proxying: alter the destination IP of the packet to the machine itself. <pre> proto tcp dport http REDIRECT to-ports 3128; proto tcp dport http REDIRECT to-ports 3128 random;</pre> </dd> <dt><a name="same" class="item">SAME</a></dt> <dd> Similar to SNAT, but a client is mapped to the same source IP for all its connections. <pre> SAME to 1.2.3.4-1.2.3.7; SAME to 1.2.3.8-1.2.3.15 nodst; SAME to 1.2.3.16-1.2.3.31 random;</pre> </dd> <dt><a name="secmark" class="item">SECMARK</a></dt> <dd> This is used to set the security mark value associated with the packet for use by security subsystems such as SELinux. It is only valid in the mangle table. <pre> SECMARK selctx "system_u:object_r:httpd_packet_t:s0";</pre> </dd> <dt><a name="flag" class="item">SET [add-set|del-set] [setname] [flag(s)]</a></dt> <dd> Add the IP to the specified set. See <a href="http://ipset.netfilter.org/">http://ipset.netfilter.org/</a> <pre> proto icmp icmp-type echo-request SET add-set badguys src;</pre> </dd> <dt><a name="snat_to_ip_address_ip_range_ip_port_range" class="item">SNAT to [ip-address|ip-range|ip-port-range]</a></dt> <dd> Change the source address of the packet. <pre> SNAT to 1.2.3.4; SNAT to 1.2.3.4:20000-30000; SNAT to 1.2.3.4 random;</pre> </dd> <dt><a name="tcpmss" class="item">TCPMSS</a></dt> <dd> Alter the MSS value of TCP SYN packets. <pre> TCPMSS set-mss 1400; TCPMSS clamp-mss-to-pmtu;</pre> </dd> <dt><a name="tos_set_tos_value" class="item">TOS set-tos [value]</a></dt> <dd> Set the tcp package Type Of Service bit to this value. This will be used by whatever traffic scheduler is willing to, mostly your own linux-machine, but maybe more. The original tos-bits are blanked and overwritten by this value. <pre> TOS set-tos Maximize-Throughput; TOS and-tos 7; TOS or-tos 1; TOS xor-tos 4;</pre> Type "iptables -j TOS -h" for details. </dd> <dt><a name="ttl" class="item">TTL</a></dt> <dd> Modify the TTL header field. <pre> TTL ttl-set 16; TTL ttl-dec 1; # decrease by 1 TTL ttl-inc 4; # increase by 4</pre> </dd> <dt><a name="ulog" class="item">ULOG</a></dt> <dd> Log packets to a userspace program. <pre> ULOG ulog-nlgroup 5 ulog-prefix "Look at this: "; ULOG ulog-cprange 256; ULOG ulog-qthreshold 10;</pre> </dd> </dl> <hr /> <h1><a name="other_domains">OTHER DOMAINS</a></h1> Since version 2.0, ferm supports not only ip and ip6, but also arp (ARP tables) and eb (ethernet bridging tables). The concepts are similar to iptables. <h2><a name="arptables_keywords">arptables keywords</a></h2> <dl> <dt><a name="source_ip_destination_ip" class="item">source-ip, destination-ip</a></dt> <dd> Matches the source or destination IPv4 address. Same as saddr and daddr in the ip domain. </dd> <dt><a name="source_mac_destination_mac" class="item">source-mac, destination-mac</a></dt> <dd> Matches the source or destination MAC address. </dd> <dt><a name="interface_outerface" class="item">interface, outerface</a></dt> <dd> Input and output interface. </dd> <dt><a name="h_length" class="item">h-length</a></dt> <dd> Hardware length of the packet. <pre> chain INPUT h-length 64 ACCEPT;</pre> </dd> <dt><a name="opcode" class="item">opcode</a></dt> <dd> Operation code, for details see the <code>iptables(8)</code>. <pre> opcode 9 ACCEPT;</pre> </dd> <dt><a name="h_type" class="item">h-type</a></dt> <dd> Hardware type. <pre> h-type 1 ACCEPT;</pre> </dd> <dt><a name="proto_type" class="item">proto-type</a></dt> <dd> Protocol type. <pre> proto-type 0x800 ACCEPT;</pre> </dd> <dt><a name="mangling" class="item">Mangling</a></dt> <dd> The keywords mangle-ip-s, mangle-ip-d, mangle-mac-s, mangle-mac-d, mangle-target may be used for ARP mangling. See <code>iptables(8)</code> for details. </dd> </dl> <h2><a name="ebtables_keywords">ebtables keywords</a></h2> <dl> <dt><a name="proto" class="item">proto</a></dt> <dd> Matches the protocol which created the frame, e.g. IPv4 or PPP. For a list, see /etc/ethertypes. </dd> <dt><a name="interface_outerface2" class="item">interface, outerface</a></dt> <dd> Physical input and output interface. </dd> <dt><a name="logical_in_logical_out" class="item">logical-in, logical-out</a></dt> <dd> The logical bridge interface. </dd> <dt><a name="saddr_daddr" class="item">saddr, daddr</a></dt> <dd> Matches source or destination MAC address. </dd> <dt><a name="match_modules" class="item">Match modules</a></dt> <dd> The following match modules are supported: 802.3, arp, ip, mark_m, pkttype, stp, vlan, log. </dd> <dt><a name="target_extensions" class="item">Target extensions</a></dt> <dd> The following target extensions are supported: arpreply, dnat, mark, redirect, snat. Please note that there is a conflict between --mark from the mark_m match module and -j mark. Since both would be implemented with the ferm keyword mark, we decided to solve this by writing the target's name in uppercase, like in the other domains. The following example rewrites mark 1 to 2: <pre> mark 1 MARK 2;</pre> </dd> </dl> <hr /> <h1><a name="advanced_features">ADVANCED FEATURES</a></h1> <h2><a name="variables">Variables</a></h2> In complex firewall files, it is helpful to use variables, e.g. to give a network interface a meaningful name. To set variables, write: <pre> @def $DEV_INTERNET = eth0; @def $PORTS = (http ftp); @def $MORE_PORTS = ($PORTS 8080);</pre> In the real ferm code, variables are used like any other keyword parameter: <pre> chain INPUT interface $DEV_INTERNET proto tcp dport $MORE_PORTS ACCEPT;</pre> Note that variables can only be used in keyword parameters ("192.168.1.1", "http"); they cannot contain ferm keywords like "proto" or "interface". Variables are only valid in the current block: <pre> @def $DEV_INTERNET = eth1; chain INPUT { proto tcp { @def $DEV_INTERNET = ppp0; interface $DEV_INTERNET dport http ACCEPT; } interface $DEV_INTERNET DROP; }</pre> will be expanded to: <pre> chain INPUT { proto tcp { interface ppp0 dport http ACCEPT; } interface eth1 DROP; }</pre> The "def $DEV_INTERNET = ppp0" is only valid in the "proto tcp" block; the parent block still knows "set $DEV_INTERNET = eth1". Include files are special - variables declared in an included file are still available in the calling block. This is useful when you include a file which only declares variables. <h2><a name="automatic_variables">Automatic variables</a></h2> Some variables are set internally by ferm. Ferm scripts can use them just like any other variable. <dl> <dt><a name="_filename" class="item">$FILENAME</a></dt> <dd> The name of the configuration file. </dd> <dt><a name="_domain" class="item">$DOMAIN</a></dt> <dd> The current domain. One of ip, ip6, arp, eb. </dd> <dt><a name="_table" class="item">$TABLE</a></dt> <dd> The current netfilter table. </dd> <dt><a name="_chain" class="item">$CHAIN</a></dt> <dd> The current netfilter chain. </dd> </dl> <h2><a name="functions">Functions</a></h2> Functions are similar to variables, except that they may have parameters, and they provide ferm commands, not values. <pre> @def &FOO() = proto (tcp udp) dport domain; &FOO() ACCEPT;</pre> <pre> @def &TCP_TUNNEL($port, $dest) = { table filter chain FORWARD interface ppp0 proto tcp dport $port daddr $dest outerface eth0 ACCEPT; table nat chain PREROUTING interface ppp0 proto tcp dport $port daddr 1.2.3.4 DNAT to $dest; }</pre> <pre> &TCP_TUNNEL(http, 192.168.1.33); &TCP_TUNNEL(ftp, 192.168.1.30); &TCP_TUNNEL((ssh smtp), 192.168.1.2);</pre> A function call which contains a block (like '{...}') must be the last command in a ferm rule, i.e. it must be followed by ';'. The '&FOO()' example does not contain a block, thus you may write 'ACCEPT' after the call. To circumvent this, you can reorder the keywords: <pre> @def &IPSEC() = { proto (esp ah); proto udp dport 500; } chain INPUT ACCEPT &IPSEC();</pre> <h2><a name="backticks">Backticks</a></h2> With backticks, you may use the output of an external command: <pre> @def $DNSSERVERS = `grep nameserver /etc/resolv.conf | awk '{print $2}'`; chain INPUT proto tcp saddr $DNSSERVERS ACCEPT;</pre> The command is executed with the shell (/bin/sh), just like backticks in perl. ferm does not do any variable expansion here. The output is then tokenized, and saved as a ferm list (array). Lines beginning with '#' are ignored; the other lines may contain any number of values, separated by whitespace. <h2><a name="includes">Includes</a></h2> The @include keyword allows you to include external files: <pre> @include 'vars.ferm';</pre> The file name is relative to the calling file, e.g. when including from /etc/ferm/ferm.conf, the above statement includes /etc/ferm/vars.ferm. Variables and functions declared in an included file are still available in the calling file. include works within a block: <pre> chain INPUT { @include 'input.ferm'; }</pre> If you specify a directory (with a trailing '/'), all files in this directory are included, sorted alphabetically: <pre> @include 'ferm.d/';</pre> With a trailing pipe symbol, ferm executes a program and parses its output: <pre> @include '/root/generate_ferm_rules.sh $HOSTNAME|'</pre> <h2><a name="conditionals">Conditionals</a></h2> The keyword @if introduces a conditional expression: <pre> @if $condition DROP;</pre> A value is evaluated true just like in Perl: zero, empty list, empty string are false, everything else is true. Examples for true values: <pre> (a b); 1; 'foo'; (0 0)</pre> Examples for false values: <pre> (); 0; '0'; ''</pre> There is also @else: <pre> @if $condition DROP; @else REJECT;</pre> Note the semicolon before the @else. It is possible to use curly braces after either @if or @else: <pre> @if $condition { MARK set-mark 2; RETURN; } @else { MARK set-mark 3; }</pre> Since the closing curly brace also finishes the command, there is no need for semicolon. There is no @elsif, use @else @if instead. Example: <pre> @def $have_ipv6 = `test -f /proc/net/ip6_tables_names && echo 1 || echo`; @if $have_ipv6 { domain ip6 { # .... } }</pre> <h2><a name="hooks">Hooks</a></h2> To run custom commands, you may install hooks: <pre> @hook pre "echo 0 >/proc/sys/net/ipv4/conf/eth0/forwarding"; @hook post "echo 1 >/proc/sys/net/ipv4/conf/eth0/forwarding"; @hook flush "echo 0 >/proc/sys/net/ipv4/conf/eth0/forwarding";</pre> The specified command is executed using the shell. "pre" means run the command before applying the firewall rules, and "post" means run the command afterwards. "flush" hooks are run after ferm has flushed the firewall rules (option --flush). You may install any number of hooks. <hr /> <h1><a name="built_in_functions">BUILT-IN FUNCTIONS</a></h1> There are several built-in functions which you might find useful. <h2><a name="_resolve__hostname1_hostname2______">@resolve((hostname1 hostname2 ...))</a></h2> Usually, host names are resolved by iptables. To let ferm resolve host names, use the function @resolve: <pre> saddr @resolve(my.host.foo) proto tcp dport ssh ACCEPT; saddr @resolve((another.host.foo third.host.foo)) proto tcp dport openvpn ACCEPT;</pre> Note the double parentheses in the second line: the inner pair for creating a ferm list, and the outer pair as function parameter delimiters. This function currently only resolves A records (i.e. IPv4 addresses), rendering it useless for the ip6 domain. Be careful with resolved host names in firewall configuration. DNS requests may block the firewall configuration for a long time, leaving the machine vulnerable, or they may fail. <hr /> <h1><a name="recipes">RECIPES</a></h1> The ./examples/ directory contains numerous ferm configuration which can be used to begin a new firewall. This sections contains more samples, recipes and tricks. <h2><a name="easy_port_forwarding">Easy port forwarding</a></h2> Ferm function make routine tasks quick and easy: <pre> @def &FORWARD_TCP($proto, $port, $dest) = { table filter chain FORWARD interface $DEV_WORLD outerface $DEV_DMZ daddr $dest proto $proto dport $port ACCEPT; table nat chain PREROUTING interface $DEV_WORLD daddr $HOST_STATIC proto $proto dport $port DNAT to $dest; }</pre> <pre> &FORWARD_TCP(tcp, http, 192.168.1.2); &FORWARD_TCP(tcp, smtp, 192.168.1.3); &FORWARD_TCP((tcp udp), domain, 192.168.1.4);</pre> <h2><a name="remote_ferm">Remote ferm</a></h2> If the target machine is not able to run ferm for some reason (maybe an embedded device without Perl), you can edit the ferm configuration file on another computer and let ferm generate a shell script there. Example for OpenWRT: <pre> ferm --remote --shell mywrt/ferm.conf >mywrt/firewall.user chmod +x mywrt/firewall.user scp mywrt/firewall.user mywrt.local.net:/etc/ ssh mywrt.local.net /etc/firewall.user</pre> <hr /> <h1><a name="options">OPTIONS</a></h1> <dl> <dt><a name="noexec" class="item">--noexec</a></dt> <dd> Do not execute the <code>iptables(8)</code> commands, but skip instead. This way you can parse your data, use --lines to view the output. </dd> <dt><a name="flush" class="item">--flush</a></dt> <dd> Clears the firewall rules and sets the policy of all chains to ACCEPT. ferm needs a configuration file for that to determine which domains and tables are affected. </dd> <dt><a name="lines" class="item">--lines</a></dt> <dd> Show the firewall lines that were generated from the rules. They will be shown just before they are executed, so if you get error messages from <code>iptables(8)</code> etc., you can see which rule caused the error. </dd> <dt><a name="interactive" class="item">--interactive</a></dt> <dd> Apply the firewall rules and ask the user for confirmation. Reverts to the previous ruleset if there is no valid user response within 30 seconds. This is useful for remote firewall administration: you can test the rules without fearing to lock yourself out. </dd> <dt><a name="help" class="item">--help</a></dt> <dd> Show a brief list of available commandline options. </dd> <dt><a name="version" class="item">--version</a></dt> <dd> Shows the version number of the program. </dd> <dt><a name="fast" class="item">--fast</a></dt> <dd> Enable fast mode: ferm generates an iptables-save(8) file, and installs it with iptables-restore(8). This is much faster, because ferm calls <code>iptables(8)</code> once for every rule by default. Fast mode is enabled by default since ferm 2.0, deprecating this option. </dd> <dt><a name="slow" class="item">--slow</a></dt> <dd> Disable fast mode, i.e. run <code>iptables(8)</code> for every rule, and don't use iptables-restore(8). </dd> <dt><a name="shell" class="item">--shell</a></dt> <dd> Generate a shell script which calls iptables-restore(8) and prints it. Implies --fast --lines. </dd> <dt><a name="remote" class="item">--remote</a></dt> <dd> Generate rules for a remote machine. Implies --noexec and --lines. Can be combined with --shell. </dd> <dt><a name="domain_ip_ip62" class="item">--domain {ip|ip6}</a></dt> <dd> Handle only the specified domain. ferm output may be empty if the domain is not configured in the input file. </dd> <dt><a name="def_name_value" class="item">--def '$name=value'</a></dt> <dd> Override a variable defined in the configuration file. </dd> </dl> <hr /> <h1><a name="see_also">SEE ALSO</a></h1> <code>iptables(8)</code> <hr /> <h1><a name="requirements">REQUIREMENTS</a></h1> <h2><a name="operating_system">Operating system</a></h2> Linux 2.4 or newer, with netfilter support and all netfilter modules used by your firewall script <h2><a name="software">Software</a></h2> iptables and perl 5.6 <hr /> <h1><a name="bugs">BUGS</a></h1> Bugs? What bugs? If you find a bug, please tell us: <a href="mailto:ferm@foo-projects.org">ferm@foo-projects.org</a> <hr /> <h1><a name="copyright">COPYRIGHT</a></h1> Copyright (C) 2001-2009 Max Kellermann <<a href="mailto:max@foo-projects.org">max@foo-projects.org</a>>, Auke Kok <<a href="mailto:sofar@foo-projects.org">sofar@foo-projects.org</a>> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA <hr /> <h1><a name="author">AUTHOR</a></h1> Max Kellermann <<a href="mailto:max@foo-projects.org">max@foo-projects.org</a>>, Auke Kok <<a href="mailto:sofar@foo-projects.org">sofar@foo-projects.org</a>> </body> </html>